Click any tag below to further narrow down your results
Links
The author, a veteran hardware and software hacker, walks through how they use AI agents with Ghidra, radare2, and Python/Rust tooling to reverse engineer devices and software far faster than they could by hand. The post pairs a workflow (documentation files, a hypothesis-testing loop, probes and logging) with a list of projects like custom synth firmware and camera control apps.
- The workflow has the agent document findings in markdown files and run a hypothesis loop (state a guess, design an experiment, record the result) to stop it going in circles.
- The author uses DeepSeek with Ghidra's MCP bridge, and says current models handle raw x86 or ARM disassembly reasonably well.
- Claimed results over six months include firmware for Arturia MiniFreak, Teenage Engineering OP-Z, and Akai MPC Sample, plus wireless control of Sony Alpha cameras.
- The author stresses that human expertise is still needed to steer agents away from narrow, unproductive approaches by reading their reasoning traces.
The author breaks any AI agent into three parts (model, loop, tools) and argues that where each one runs determines cost, capability, privacy, and security. It's a practical checklist for judging what an agent product can and can't safely do.
- An agent is three things: the model (its "smarts"), the agentic loop (which shapes the UX), and the tools (its capabilities and blast radius). Tools and loop together are often called "the harness."
- Hosting the model yourself is the only way to be confident your data isn't used for training, and local models make sense for slow overnight jobs like OCR on private documents.
- Running code tools is the riskiest part: VMs are the gold standard for sandboxing, while local agents have a bigger blast radius for leaking secrets from untrusted content.
- LLM features break SaaS cost models, since one user prompt can cost real money, which is why "bring your own model" options are likely to spread.
Open Code Review is an open-source CLI tool that uses LLMs to review code diffs and full files with higher precision than general-purpose AI agents while using 9x fewer tokens. It combines deterministic engineering (file selection, rule matching, positioning) with an agent for dynamic decisions, and has been validated across 200 real pull requests from 50 open-source projects.
- Achieves significantly higher precision and F1 scores than Claude Code with the same underlying model, consuming only ~1/9 of the tokens and completing reviews faster
- Uses hard constraints (precise file selection, smart bundling, fine-grained rule matching, external positioning modules) to eliminate common AI agent failures like incomplete coverage and position drift
- Built on production data from Alibaba's internal use across two years serving tens of thousands of developers and identifying millions of defects